[Data Object Grid] Respect fallback languages for localized fields#1787
Merged
markus-moser merged 11 commits into2025.4from Apr 29, 2026
Merged
Conversation
Not up to standards ⛔
|
599e2a0 to
dd926fc
Compare
dd926fc to
713ab60
Compare
…solverInterface for consistency Replace contract interfaces with non-contract versions to match the existing pattern in studio-backend-bundle (e.g. WebsiteSettingsService, LanguageService, ApiContextSubscriber).
martineiber
requested changes
Apr 29, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Introduces the
applyFallbackLanguagesflag on the data object grid request body. When set totrue, empty localized field values walk the configured fallback language chain (and fall back to the system default language as a last resort) instead of returning null.The flag defaults to
falseso existing grid behaviour is completely unaffected. It is implemented via Pimcore's built-inLocalizedfield::setGetFallbackValues()mechanism — no custom fallback chain logic.Companion PR: pimcore/studio-ui-bundle#3424
Part of pimcore/studio-ui-bundle#3405